Information acquisition using a scalable wireless geocast protocol

ABSTRACT

Information is acquired from a geographically-distributed sensor network using a scalable wireless geocast protocol. Geographically distributed networks of unattended sensors are placed at desired locations to collect various types of information, such as, for example, environmental parameters, temperature, humidity, rainfall, heat signatures, video, audio, seismic activity, and/or wind conditions. To acquire information, a query is provided to the geographic area at which the sensors are located utilizing the geocast protocol. Delivery of the query is based on a physical location of a region in which a sensor network is located, the type of information being queried, and/or temporal conditions. Each sensor that receives a query determines if all requirements/conditions are satisfied. If so, the query is accepted and processed by the recipient sensor, and responded to accordingly. Responses to queries are provided via the geocast protocol.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/863,626, filed Sep. 24, 2015, which is a continuation of U.S. patentapplication Ser. No. 13/169,892, filed Jun. 27, 2011, now U.S. Pat. No.9,161,158, issued Oct. 13, 2015, both of which are entitled “InformationAcquisition Using A Scalable Wireless Geocast Protocol.” The contents ofthe above-referenced applications are incorporated by reference hereinin their entirety.

TECHNICAL FIELD

The technical field generally relates to acquisition of information andmore specifically to acquiring and/or accessing information via ascalable, wireless, geographic broadcast (“geocast”) protocol.

BACKGROUND

Typically, to acquire data, a sensor is placed at a desired location,and the sensor is accessed to acquire data. Depending upon the desiredlocation, acquisition of data could be quite difficult. For example, ifthe desired location is in a remote area (e.g., mountainous area with noaccess roads), access to the sensor could be difficult. Further, if theexact location of the sensor is not known, acquisition of data from thesensor could be difficult, if not impossible. For example, in the caseof a sensor dropped from an aircraft into a forest, acquisition of datafrom the sensor could be impossible without knowing the sensor'slocation. As another example, a sensor could be dropped into an ocean orsea. However, as the sensor drifts, due to currents or the like, findingthe sensor could be arduous. Depending upon the type of data to beacquired, acquisition of data could be quite difficult. For example,access to a sensor placed behind enemy lines could be difficult anddangerous. Also problematic, is knowing if a sensor is working properly.Typically, a sensor is accessed to acquire data, and only then, uponreceiving no data or receiving corrupted data, can the conclusion bemade that the sensor has failed. The foregoing difficulties could begreatly exacerbated when working with multiple sensors.

SUMMARY

Information is acquired and/or accessed from ageographically-distributed sensor network using a scalable wirelessgeographic broadcast (“geocast”) protocol. In an example embodiment,geographically distributed networks of unattended sensors are placed atdesired locations. Sensors can be placed across an area of geography tocollect various types of information. For example, sensors can acquireinformation pertaining to environmental parameters, temperature,humidity, rainfall, heat signatures, video, audio, seismic activity,wind conditions, or the like. To acquire information, a query isprovided to the geographic area at which the sensors are locatedutilizing a geocast protocol. Delivery of the query is based on aphysical location (or locations) of a region (e.g., geographic area) inwhich a sensor or sensor network is located. Queries are accepted bysensors satisfying the requirements/conditions of the query. Acceptanceof the query by a sensor can be based on any appropriate additionalcondition or conditions, such as the type of information being queried(e.g., environmental parameter, temperature, humidity, rainfall, heatsignature, video, audio, seismic activity, wind conditions, etc.),and/or a temporal condition (e.g., time period, time limit, beginningtime, ending time, etc.). In an example embodiment, a physical locationis incorporated as part of an addressing protocol in order to routequeries to intended sensors at the appropriate locations. Each sensorthat receives a query determines if all conditions are satisfied. If so,the query is accepted and processed by the recipient sensor, andresponded to accordingly. If not, the query is not accepted by thesensor, but may be retransmitted via the geocast protocol. Responses toqueries are provided via the geocast protocol.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example mobile ad hoc network in which informationacquisition/access via a geocast protocol may be implemented.

FIG. 2 illustrates example communications in an ad hoc network in whichinformation acquisition/access via a geocast protocol can be implementedvia a WiFi access point.

FIG. 3 illustrates an example mobile ad hoc network in which informationacquisition/access via a geocast protocol can be implemented utilizingtiered geocasting and forwarding zones.

FIG. 4, comprising FIG. 4A-FIG. 4E depict example geocast regions orboundaries.

FIG. 5 is a flow diagram of an example process for acquiring/accessinginformation via a geocast protocol.

FIG. 6 is a flow diagram of another example process foracquiring/accessing information via a geocast protocol.

FIG. 7 is a flow diagram of another example process foracquiring/accessing information via a geocast protocol utilizing reversepath forwarding.

FIG. 8 is a flow diagram of an example process of geocast-basedcommand/control messaging.

FIG. 9 is a flow diagram of another example process foracquiring/accessing information via a geocast protocol.

FIG. 10 is a block diagram of an example wireless communicationsdevice/sensor configurable to facilitate information acquisition via ascalable wireless geocast protocol.

FIG. 11 depicts an overall block diagram of an exemplary packet-basedmobile cellular network environment, such as a GPRS network, withinwhich information acquisition via a scalable wireless geocast protocolcan be implemented.

FIG. 12 illustrates an architecture of a typical GPRS network withinwhich information acquisition via a scalable wireless geocast protocolcan be implemented.

FIG. 13 illustrates an exemplary block diagram view of a GSM/GPRS/IPmultimedia network architecture within information acquisition via ascalable wireless geocast protocol can be implemented.

FIG. 14 illustrates a PLMN block diagram view of an exemplaryarchitecture in which the information acquisition via a scalablewireless geocast protocol may be incorporated.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Information acquisition using a scalable wireless geocast protocolprovides the capability to acquire/access information from ageographically distributed sensors. Queries for information andresponses thereto are based on conditions being satisfied, such as ageographic location, type of information being sought, and/or a timeframe of interest. Relatively low cost communications capable sensorscan placed within an area of geography to collect information.Utilization of the geocast protocol, allows for scalable expansion ofsensor networks.

Example applications of information acquisition using a scalablewireless geocast protocol include government (military, disaster relief,intelligence community, emergency response, etc.,), enterprise (campusand physical plant monitoring), home networking, and smart gridapplications. For example, when an agent enters an area, such as a humansoldier walking patrol through a valley or forest, the agent cantransmit a query using the scalable wireless geocast protocol to thearea or a sub-region of the area. Sensors in the area can deliver thequery message to other sensors. The sensors within the addressed regioncan respond by transmitting back, utilizing the geocast protocol (orother appropriate messaging protocol), to the agent their responsescontaining the desired information. Various other example applicationscan utilize a vehicle traveling a road through an area to provide aquery, an aerial vehicle (e.g., UAV) overflying an area to provide aquery, or the like.

Information acquisition using a scalable wireless geocast protocolprovides networking that is handled in real time, on the fly, withoutneed for provisioning or maintenance of the network, server nodes, orother overhead. Further, information acquisition using a scalablewireless geocast protocol can be easily scaled to handle very large anddense networks of sensors (e.g. hundreds to thousands in an area). Theentity providing the initial query need not know in advance whichsensors are in the receiving area nor which are working or workable atthe time the query is provided. The, the geocast protocol can operate inan ad hoc fashion, device-to-device, sensor-to-sensor, such thatinformation acquisition can be accomplished in remote areas that do nothave the benefit of coverage by infrastructure based networks (e.g.,cellular coverage, wireless radio coverage, satellite coverage, etc.).

In an example embodiment, geocasting refers to addressing, transferring,and delivering a message (e.g., query, response, etc.) via a network ina accordance with a geocast protocol wherein the address comprises ageocast region, and/or other conditions. Geocasting provides the abilityto transfer a message, via a geocast protocol, from a sender to eachmember of a set of devices (e.g., sensors) currently occupying thegeocast region and, if applicable, satisfying appropriate conditions.Geocasting can provide very efficient tracking of sets of devices (e.g.,sensors). Geocasting allows a network to propagate a message completelywithout need for any centralized server based on local deviceinformation.

Geocasting is particularly suited to acquiring information from largenumbers of devices (e.g., sensors) and/or highly mobile devices (e.g.,sensors) without requiring connection to an infrastructure-basedcommunications network. A mobile ad hoc network is an example of such aset of devices (e.g., sensors). Mobile ad hoc networks extend the reachof data networking into areas and scenarios in whichinfrastructure-based networking is impossible or impractical. Forexample, mobile ad hoc networks can allow first responders to usenetworked messaging and information applications in a zone where thenetwork infrastructure has been destroyed by a disaster. Mobile ad hocnetworks can provide military units operating in battlefield situationslacking infrastructure the same types of benefits asinfrastructure-based networks. Mobile ad hoc networks can allownetworking among low resource nodes, such as man-worn devices powered bylightweight wearable batteries, by allowing units to relay each other'sshort-range transmissions, instead of each unit transmitting long rangedirectly to the destination. Some mobile ad hoc networks, such asmilitary mobile ad hoc networks, require high security, due to thelife-critical nature of battlefield secrecy.

Various embodiments of information acquisition/access via a geocastprotocol are described herein. The described embodiments are merelyexamples that may be embodied in various and alternative forms, andcombinations thereof. As used herein, for example, “exemplary,” andsimilar terms, refer expansively to embodiments that serve as anillustration, specimen, model, or pattern. The figures are notnecessarily to scale and some features may be exaggerated or minimized,such as to show details of particular components. In some instances,well-known components, systems, materials, or methods have not beendescribed in detail in order to avoid obscuring the instant disclosure.Therefore, specific structural and functional details disclosed hereinare not to be interpreted as limiting, but rather as a basis for theclaims and as a representative basis for teaching one skilled in the arthow to employ the teachings instant application in various ways.

While the herein description includes a general context ofcomputer-executable instructions, information acquisition/access via ageocast protocol also can be implemented in combination with otherprogram modules and/or as a combination of hardware and software. Theterm “application,” or variants thereof, is used expansively herein toinclude routines, program modules, programs, components, datastructures, algorithms, and the like. Applications can be implemented onvarious system configurations, including single-processor ormultiprocessor systems, minicomputers, mainframe computers, personalcomputers, hand-held computing devices, microprocessor-based,programmable consumer electronics, combinations thereof, or the like. Itis to be understood that a processor comprises hardware or a combinationof hardware and software.

In an example embodiment, information acquisition/access via a geocastprotocol is implemented via a scalable, wireless, geographic broadcast(“geocast”) protocol, and devices (e.g., sensors) taking part ininformation acquisition/access via a geocast protocol are programmedwith an application, which uses geolocation information obtained from alocating system, such as, for example, a global positioning system(GPS), or the like. Geocast protocols differ from a traditional Internetprotocol (IP) such as the uniform datagram protocol (UDP) in thatmessages are addressed to a destination geocast region instead of an IPaddress, such as an UDP address. Utilizing the geocast protocol, devices(e.g., sensors) in a target area do not need to register to a groupaddress, as required of some other protocols. In some exampleembodiments, each geocast data packet is assigned, at origination, aglobally unique packet serial number. The unique packet serial number isread by participating devices according to the protocol to, for example,determine whether a particular data packet is being received for a firsttime or has been received before. The packet serial number and all otherpacket information may be positioned in a header or body of the datapacket.

Although basic geocasting over only a single network (e.g., long-rangenetwork) enables communications in some situations where traditionalnetworking is impractical or inadequate, it is in some embodimentspreferable to selectively geocast over one or more of two or morenetworks (i.e., tiers) versus the flat configuration of a singlenetwork. The tiered geocast protocol of the present disclosure improveson single-network geocasting by providing the heuristics, or decisionrules, for selectively propagating geocast data packets within arelatively short-range, peer-to-peer network, and bridging packets ontoa long-range network for long-distance transport depending on variouscircumstances. Each participating device (e.g., sensor) and other device(e.g., sensor) have forwarding rules, including geographical parameters,and a look-up table for use in implementing the rules.

In one embodiment, the geocast system is configured such that atransmitting device (e.g., sensor) receives a confirmation that ageocast data packet was transmitted successfully. For example, it iscontemplated that at least one of the devices (e.g., sensors) in ageocasting destination region, even if not a device (e.g., sensor)actively participating in responding to a query, could return a geocastconfirmation data packet indicating that the packet was received by adevice (e.g., sensor) in the region. In one contemplated embodiment,although the protocol is based on a geographical address and not adevice-specific address, a device-specific address, or other appropriateidentifier, of a target device (e.g., sensor) could be included in ageocast and the target device (e.g., sensor) could initiate inclusion ina return geocast data packet of a confirmation of receipt message to theoriginator of the query.

In addition, in some embodiments, a geocast data packet includes one ormore fields, such as in a header or body of the packet, in whichinformation related to a path taken by a packet is recorded. Forexample, a receiving device (e.g., sensor) receiving a geocast canretrieve data from the geocast header to identify an ordered list of thedevices (e.g., sensors) whose transmissions led to the receiving device(e.g., sensor) receiving it. In this way, path discovery is integratedinto the transmission process. Any device (e.g., sensor) can also usethis information to send a source-routed unicast back to any device(e.g., sensor) along the path, which is termed reverse-path forwarding(RPF).

Although a two-tiered communication system, including a firstshort-range peer-to-peer network and a long-range network, is describedherein, the information acquisition/access via a geocast protocolapplication of the present disclosure may be implemented in connectionwith a protocol and communication system using other types of networksas well as or instead of those described herein, and in connection withmore than two network tiers.

Propagations over the short-range network are made between devicesprogrammed with the scalable tiered geocast protocol, whereby adjacentdevices (e.g., sensors) are within range of each other, such as radiorange (e.g., 100 meters). The devices (e.g., sensors) and tiered geocastprotocol are configured to transmit geocast data packets over one ormore short-range networks, including existing wireless local areanetworks (WLANs), such an IEEE 802.11 network, or the like. As anexample, when a first device (e.g., sensor) is about 900 meters from anedge of a geocasting region including a second device (e.g., sensor), ageocast data packet from the first device (e.g., sensor) could bebroadcasted and participating intermediate devices (e.g., sensors) couldreceive and retransmit the geocast data packet until it reached thegeocast region, without need for transmission over an Internet router orother base station. In this example, depending on the location of aretransmitting device (e.g., sensor), the geocast data packet can bebroadcast to the geocast region in one or two hops.

To better understand information acquisition/access via a geocastprotocol and applications thereof, a description of mobile ad hocnetworks is provided. It is to be understood however, that applicationsof information acquisition/access via a geocast protocol are not limitedto mobile ad hoc networks. Rather, information acquisition/access via ageocast protocol is applicable to any appropriate device (e.g., sensors)or group of devices (e.g., sensors).

A mobile ad hoc network comprises communications devices (also referredto as nodes) that communicate with each other via geographicalbroadcasting, referred to as geocasting. Geocasting is described in U.S.Pat. No. 7,525,933, entitled “System And Method For Mobile Ad HocNetwork,” filed Nov. 30, 2005, issued Apr. 28, 2009, and is incorporatedby reference herein in its entirety. Geocasting uses a protocol in whichan IP address is replaced with a geographic address. Thus, each geocastmessage comprises an indication of a location of a geographic region ofintended reception of the geocast message. Generally, a packet is sentto every communications device located within a specific geographicregion. The packet can contain an indication of the location of thesender, an indication of the geographic region, a payload, or acombination thereof, or the like. The communications devices in thegeographic region, and any other communications devices that cancommunicate with them, are referred to, collectively, as a mobile ad hocnetwork. No registration is required to become a member of the mobile adhoc network. Any communications device in the mobile ad hoc network cansend a message to any or every communications device in the mobile adhoc network. As communications devices move within communications rangeof any member of the mobile ad hoc network, they can become members ofthe mobile ad hoc network without requiring registration. Thecommunications devices of the ad hoc network of communications devicescommunicate with each other. The ad hoc network of communicationsdevices does not require base station terminals to controlcommunications between the mobile devices. In example embodiments, basestations or routers may be used to relay messages between differentmobile ad hoc networks, or to use other network transports such as othertraditional internet protocol networks, such as the internet, to bridgemessages between mobile ad hoc networks. Each communications device iscapable of receiving and/or transmitting data packets to and/or fromother communications devices in the mobile ad hoc network.

In an example embodiment, a communications device transfers packets toother communications devices according to heuristic decision rules thatdetermine whether a receiving device will re-transmit a received packet.These rules effectively guide packets to their destinations and controlcommunication traffic within the ad hoc network. The decision rulesachieve this control by using statistics obtained and recorded by acommunications device as it receives packets transmitted withinreception range within its environment. This distributed packet transfermechanism results in packets “flowing” to and throughout the geocastregion specified in each packet. The communications devices in thegeocast region receive and process each distinct packet, typicallyrendering the content to the user via a user interface of acommunications device. Two packets are distinct if they contain distinctgeocast identifiers. However, a re-transmitted copy of a packetgenerally will contain the same geocast identifier as the originalpacket.

FIG. 1 illustrates an example mobile ad hoc network in which informationacquisition/access via a geocast protocol may be implemented.Communications devices, also referred to herein as devices, sensors, ornodes, in the mobile ad hoc network can communicate via RF encoded withgeographic information, via Bluetooth technology, via Wi-Fi (e.g., inaccordance with the 802.11 standard), or the like, or any combinationthereof. For example, as depicted in FIG. 1, communication devices 12,14, 16, 18, and 20 form a mobile ad hoc network. As shown in FIG. 1,communication device 12 communicates with communications device 14directly (e.g., via Bluetooth). Communication device 14 communicateswith communications device 16, and thus can retransmit informationreceived from communications device 12 to communications device 16, andvice versa (retransmit information received from communications device16 to communications device 12). Communications device 16 communicateswith communications devices 18 and 20, and can relay information from/tocommunications devices 18 and/or 20 to/from communications devices 12and/or 14.

Although not depicted in FIG. 1, it is possible, in a mobile ad hocnetwork, that, for a pair of nodes (A and B for example), node A canreceive from node B but node B cannot receive from node A. Thisasymmetric style of communication is potential likely in a mobile ad hocnetwork.

In an example embodiment, communications devices that receive a message,such as a query or a response, can resend the query/response inaccordance with the scalable wireless geocast protocol. For example, acommunication device's ability to retransmit a query/response can bebased on the number of times the query/response was previously received,the communication device's proximity with respect to the communicationsdevices from which the query/response was sent, and/or the communicationdevice's proximity to the geocast region. This can be implemented as athree step location-based approach, which is described in detail in theaforementioned U.S. Pat. No. 7,525,933, entitled “System And Method ForMobile Ad Hoc Network,” filed Nov. 30, 2005, issued Apr. 28, 2009.First, in accordance with the location-based approach, the receivingcommunication device determines whether it has previously received thesame query/response at least a predetermined number (N) of times. Ifnot, it retransmits the query/response over the ad hoc network ofcommunications devices. If so, the communications device progresses tothe second step and determines whether the sending communications deviceis closer than some minimum distance away. If no prior transmitter ofthe query/response was closer than some minimum distance away, thecommunications device retransmits the query/response over the ad hocnetwork of communications devices. Otherwise, the communications deviceprogresses to the third step and determines whether it is closer to thecenter of the geocast region than any sending communications device fromwhich the query/response was received. If so, the communications devicetransmits the query/response over the ad hoc network of communicationsdevices. If not, the communications device does not retransmit thequery/response.

This location-based approach prevents the receiving communicationsdevice from retransmitting a message that was most likely alreadyretransmitted by another communications device located close to it (andthus most likely reaching the same neighboring communications devicesthat it can reach). In addition, this location-based approach reducesthe chance that the communications device will retransmit the samemessage multiple times to the same neighboring communications devices.

As mentioned above, a mobile ad hoc network does not require acommunications network infrastructure or a WiFi access point. However,in an example configuration, a mobile ad hoc network can utilize WiFiaccess points and/or a communications network infrastructure.

FIG. 2 illustrates example communications in an ad hoc network in whichinformation acquisition/access via a geocast protocol can be implementedvia a WiFi access point. As depicted in FIG. 2, communication devices26, 28, 30, 36, and 38 form a mobile ad hoc network and communicationdevice 32 and 34 form another mobile ad hoc network. Coverage area 22,which is the area covered by a WiFi access point 40, coverscommunication devices 26 and 28. Coverage area 24, which is the areacovered by another WiFi access point 42 covers communication device 32.As shown in FIG. 2, communication device 34 transmits to communicationdevice 32 directly (e.g., via Bluetooth). Communication device 32retransmits to a WiFi access point 42 which in turn retransmits to theother WiFi access point 40. Communication devices 26 and 28 receive thetransmission from the WiFi access point 40, and communication device 28retransmits directly to communication device 30. And, as depicted,communication device 30 retransmits to other communication devices 36and 38.

FIG. 3 illustrates an example mobile ad hoc network in which informationacquisition/access via a geocast protocol can be implemented utilizingtiered geocasting and forwarding zones. Tiered geocasting uses longrange (LR) transmitters (such as communications devices, etc.),infrastructure, a communications network, a cellular tower, or acombination thereof, when available. Tiered geocasting assumes that atleast one tier is usable by at least one of the communications devices.A long range tier is a tier wherein characteristic message transfersbetween devices occur over a longer physical range than those over someother tier. A long range tier can be wireless, wired, or a combinationthereof.

A forwarding zone can be utilized to implement tiered geocasting. Acommon forwarding zone can be defined for all geocast packets ordifferent forwarding zones can be defined for each type of geocastpacket. Forwarding zones (as shown in FIG. 3, for example and withoutlimitation) can be defined differently in different tiers, even for thesame packet type or even same packet. Thus, forwarding heuristics can beapplied independently per tier, with bridging at multi-tier capablenodes. In an example embodiment, a communications device retransmits apacket only if the communications device is located within theforwarding zone defined for the packet's type. This determination is inaddition to the determinations described above and, if thecommunications device is not in the forwarding zone, the packet will notbe retransmitted, even if one or more of the above conditions wouldotherwise have caused a retransmission hold.

As depicted in FIG. 3, nodes (e.g., communications devices) D1, D2, D3,D4, D5, D6, and D7, are at various locations within short range (SR) andlong range (LR) tiers. All of devices D1, D2, D3, D4, D5, D6, and D7together form a mobile ad hoc network, with devices D5, D6, and D7 beinglocated in geocast region Y, hence being targets of a message sent byD1. Each communications device D1, D2, D3, D4, D5, D6, and D7 candetermine its own geographical location through any type of locationdetermination system including, for example, the Global PositioningSystem (GPS), assisted GPS (A-GPS), time difference of arrivalcalculations, configured constant location (in the case of non-movingnodes), any combination thereof, or any other appropriate means. Eachcommunications device is operable to transmit and receive packets on amobile ad hoc network. In addition, at any given time, some subset(possibly all) of the communications devices may be operable to transmitand receive packets over the long range tier network. For example,though not a limitation, in FIG. 3, devices D2, D3, and D4 can transmitand receive messages over both the short and long range tiers. Note thatthis latter fact is indicated visually in the diagram by D2, D3, and D4each having two dots (one in the short range tier and one in the longrange tier) connected by a vertical line. The long-rang tier network canbe any network in which packets can be transmitted from one long rangecapable communications device to another long range capablecommunications device. Such packet networks can include, for example, aninfrastructure-based network comprising wireless base stations (for up-and down-link) operating on a separate frequency from that used by an adhoc network. In addition, the long rang tier network also could beimplemented simply as another instance of an ad hoc network usingdistinct radio frequencies and possibly longer radio ranges.

Communications device D1 transmits the message, and communicationsdevice D2 receives the transmission from communications device D1.Communications device D2 retransmits (transmission 2 a), within theshort range tier and in accordance with the heuristics for the shortrange forwarding zone (SRFZ) as well as within the long range tier(transmission 2 b). Communications D2, with long range transmissioncapability (in the long range tier) retransmits in the long range tieras well (transmission 2 b). Communications device D3 receives thetransmission 2 b from communications device D2 and retransmits (astransmission 3) in the long range tier only. Communications device D4receives the transmission 3 from communications device D3 andretransmits both on the long and short range tiers, resulting intransmission 4 a in the long range tier and 4 b in the short range tier.Communications device D5, within geocast region Y, receives thetransmission 4 a, and in turn retransmits (transmission 5) within thegeocast region Y. Transmission 5 is received by the other devices ingeocast region Y, namely devices D6 and D7, thus completing the geocastmessage transfer.

As described above, sensors can be deployed in a geographic area.Geocast origination, destination, and termination regions can be definedby geographic parameters and may have any size and shape. As examples,the regions may be defined by three or more bounding geographiccoordinates, forming a triangle, rectangle, or other shape, or a singlegeographic coordinate and a radius or diameter, forming a geocastregion.

FIG. 4, comprising FIG. 4A-FIG. 4E depict example geocast regions orboundaries. A geocast region may be defined to be a single point 40, asdepicted in FIG. 4A. A point geocast region may be defined by alongitude value and a latitude value (not shown). A point above thesurface of the earth could be defined by providing an altitude value inaddition to longitude and latitude values. A geocast region may alsocomprise multiple single points (not shown) such as the single point 40.Location points such as point 40 may be used as the building blocks formore complex geocast region geometries, as described herein. FIG. 4Bdepicts a geocast region defined by a point 40 in combination with aradius 42. The geocast region of this example will comprise the areaenclosed by the radius, and may include the space above the area aswell. A geocast region could also be defined as the overlap regionbetween two or more circular geocast regions (not shown). FIG. 4Cdepicts a more complex geometry formed from a series of points 40interconnected with straight boundary lines. This technique of geocastregion definition is similar to the techniques typically used in thedefinition of parcels of real property. FIGS. 4D and 4E depict thecreation of one or more geocast regions within a single geographicfootprint. FIG. 4D depicts creating a geocast region for a specificfloor of a building 44. The single floor geocast region is defined asthe volume of space between upper and lower areas, each formed using aseries of points 40 set at corners of the buildings. FIG. 4E depicts analternate technique for defining a single floor geocast region inbuilding 44. Upper and lower points 40 are defined in the middle of theceiling and the floor of the geocast region respectively. The singlefloor geocast region is then defined as the volume of space between anupper area and a lower area defined by a pair of radii 42 extending fromthe middle points. Geocast regions may also be defined to change insize, geographic location, etc. with time (not shown), essentiallyallowing the creation of geocast regions in four dimensions. For examplea region corresponding to a sensor deployment region may be defined tochange size, shape, and/or geographic location over time as the numberof participating sensors fluctuates. Information defining a particulargeocast region (e.g., a series of points) can be communicated in anaddressing portion of a geocast message. Geocast sub-regions may bedefined within a particular geocast region using the above techniques.It should be noted that the techniques described with reference to FIGS.4A-4E are merely examples, and the scope of the instant disclosureshould not be limited thereto. Other sensor deployment region geometriesand techniques for defining sensor deployment regions may be recognizedby those skilled in the art, and are meant to be included within thescope of the instant disclosure.

In some embodiments, a sensor deployment geocast region can be selectedby making one or more selections on a map and/or from a list. A regioncan be selected from a list displayed on a mobile communications device,or the like. The list can comprise real world locations. For example,one can scroll through a list by touching the display surface of amobile communications device, or the like, by providing a voice command(e.g., “Scroll List”), by entering text on which to search, by movingthe device, or any appropriate combination thereof. In another exampleembodiment, the selection of a sensor deployment region, or the like canbe made by selecting a location on the map by a finger, fingers, and/orany other appropriate device, and, for example, dragging away orgesture-pinching, from the selected location to create the size of the acircle, oval, rectangular, square, polygon, or any appropriate shape(two dimensional or three dimensional) representing a destination,termination, boundary, region, or the like. In various exampleembodiments, locations, such as addresses, and/or region dimensions,building names, institution names, landmarks, etc. may be input in otherways by a player, such as by typing, gesture, and/or voice input.

FIG. 5 is a flow diagram of an example process for acquiring/accessinginformation via a geocast protocol. A query is geocast at step 50. Thequery is received at step 52. The query can be received by one of moreof the devices (e.g., sensors) as described above. In various exampleconfigurations, the query can comprise an indication of a geographicregion, an indication of a temporal condition (e.g., time frame, starttime, end time), an indication as to the type of information sought, orany combination thereof.

The indication of the geographic region can comprise an indication of aregion, such as for example a region within which intended recipientdevices (e.g., sensors) are located, or expected to be located. Theregion can be described in terms of any appropriate shape, location, orthe like. For example the region can be described as a building or groupof buildings (e.g., campus), landmark, institution (e.g., NationalInstitutes of Health, etc.), or the like. The region can be described asa geometric shape, such as a rectangle, a circle, a hexagon, anirregular shape, a curvilinear shape, or any combination thereof. Theregion can be in two or three dimensions. For example, the region can bea sphere or any appropriate three-dimensional shape. The region can bedefined in the content of communications among geocast ad hoc networkmembers. Thus, information describing the region (e.g., location, size,shape, coordinates, range of coordinates, etc.) can be contained inpackets communicated among the geocast ad hoc network devices (e.g.,sensors). The information could vary from packet to packet, vary as afunction of time (e.g., geographic region changes as sensors drift),and/or predetermined and fixed prior to communications between thedevices (e.g., sensors) of the geocast ad hoc network.

The indication as to the type of information sought can be indicative ofany appropriate information. Example types of information includeinformation pertaining to environmental parameters, temperature,humidity, rainfall, heat signatures, video, audio, seismic activity,wind conditions, or the like.

The indication of a temporal condition (e.g., time frame, start time,end time, etc.) can be indicative of a time, time period, time interval,time beginning at a start time, time leading up to an end time, or thelike during which information was gathered by the sensor and/or duringwhich devices/sensors are expected to be within the target region. Forexample, a query could be geocast requesting information that wasobtained by sensors during a previous number of hours, days, etc.,during a time frame between a start time and end time, during time aftera given start time, or the like, or any combination thereof. Forexample, the temporal conditions could include a specific time of day, awindow around a time of day, an amount of time to be added to the timethe geocast message was received to determine a time window, any numberof predetermined times or time windows, or the like. As one example, anadvertiser could geocast a coupon, for a particular product, to allrecipients located in a store of a competitor.

At step 54, it is determined if the device (e.g., sensor) receiving thequery is located within the region indicated in the query. Determinationas to whether the device (e.g., sensor) is within the region can beaccomplished by any appropriate device, apparatus, system, or the like.In an example embodiment, the device (e.g., sensor) that received thegeocast query determines if the device (e.g., sensor) is within theregion. For example, the receiving device/sensor can process the queryto extract the indication of the region. The device/sensor can comparethe device's current physical location with the region. The currentphysical location of the device/sensor can be determined in anyappropriate manner. For example, a device/sensor can determine its owngeographical location through any type of location determination systemincluding, for example, the Global Positioning System (GPS), assistedGPS (A-GPS), time difference of arrival calculations, configuredconstant location (in the case of non-moving nodes), any combinationthereof, or any other appropriate means.

If it is determined, at step 54, that the device/sensor is not withinthe region, the query is not accepted or processed by the recipientdevice/sensor, at step 56. It is to be understood that the processdepicted in FIG. 5 is not necessarily separate from retransmission(transfer) of the query. Thus, in embodiments wherein the geocast queryis retransmitted via a geocast, or other geographically-based networkprotocol, step 56 may be conducted as part of the execution of thatprotocol. Geocast processing can be used to get the message to therecipient as well as to decide if the recipient is in the set ofspecified regions.

As described above, the query can contain an indication of the type ofinformation be sought. If the query contains an indication of the typeof information being sought, the device/sensor determines if it is thecorrect device/sensor to provide the type of information being sought.For example, if the query contains an indication that temperature isbeing sought, and the recipient device/sensor is a wind sensor, thedevice/sensor is not the correct type of device/sensor. If the querydoes not contain an indication of the type of information being sought,the device/sensor will accept the query in order to provide a responseof indicative of the type of information the device/sensor has obtained.

Accordingly, if it is determined, at step 54, that the device/sensor iswithin the region, it is determined, at step 58, if the query containsan indication of the type of information being sought. If the query doesnot contain an indication of the type of information being sought, thequery is accepted by the recipient device/sensor, at step 60 If thequery does contain an indication of the type of information beingsought, it is determined, at step 62, if the recipient device/sensor isthe correct sensor (capable of providing the type of information beingsought) for providing the type of information being sought. If the typeof information being sought does not match the device/sensor'scapabilities, the process proceeds to step 56. If the type ofinformation being sought does match the device/sensor's capabilities,that is, if the recipient device/sensor is the correct type ofdevice/sensor to provide the type of information being sought, the queryis accepted by the recipient device/sensor at step 60.

A response to the query is generated at step 64. The query is processedby the recipient device/sensor, and if the query contains an indicationof a temporal condition, information obtained during the specifictemporal condition parameters is incorporated into the response. If thequery contains no indication of a temporal condition, all availableappropriate information obtained by the recipient device/sensor isincorporated into the response. Determination as to whether a temporalcondition(s) is satisfied can be accomplished in any appropriate manner.For example, the recipient device/sensor receiving the geocast querysignal can determine a time based on an internal clock of the device,and compare it to the temporal condition(s), a time provided by otherthan the device receiving the geocast query (e.g., GPS, external clock,network entity, etc.) can to be used to compare to the temporalindication(s).

In an example embodiment, depending upon the nature of the geocastprotocol, the query can be retransmitted, via a geocast, by therecipient device/sensor, at step 66.

FIG. 6 is a flow diagram of another example process foracquiring/accessing information via a geocast protocol. A query isgenerated at step 70. The query can comprise a message that includes, asdescribed above, an indication of a geographic region, an indication ofa temporal condition (e.g., time frame, start time, end time), anindication as to the type of information sought, or any combinationthereof. The message can contain a description of the desiredinformation (information being sought—wanted information), a digitalsignature, or the like, for authentication purposes, or a combinationthereof. The indication as to the type of information sought can beindicative of any appropriate information as described herein.Optionally, the message can be encrypted.

The query is geocast at step 72. The query can be geocast to anyappropriate region, location, or the like. The geocast message isreceived by a device at step 74. It is to be understood that the geocastquery can be received by multiple devices and the process depicted bysteps 74 et seq. in FIG. 6 could occur for each device that receives thegeocast query. If the message of the query was encrypted (step 76), thedevice attempts to decrypt the message at step 78. If the attempt todecrypt the message is not successful (step 80), the message isdiscarded at step 82. If the attempt to decrypt the message issuccessful (step 80), the query/message is verified at step 84. Themessage can be verified to determine if the message is authentic. In anexample configuration, the message is verified utilizing the digitalsignature that was included when generating the query (e.g., step 70).Verification utilizing a digital signature can be accomplished via anyappropriate mechanism as known. For example, the message, the query, orany appropriate portion or portions thereof can be operated on by a hashfunction to obtain a first hash value. The first hash value can beincluded with the query. The first hash value may or may not beencrypted. At step 84, the same portion or portions of the messageand/or query can be operated on by the same hash function to obtain asecond hash value. If the first hash value is the same as the secondhash value, the query/message can be determined to be authentic. If thefirst hash value is not the same as the second hash value, thequery/message can be determined not to be authentic. It is to beunderstood that the foregoing description of verifying the query/messageis an example, and not limiting. Any appropriate mechanism or techniquefor verifying the query/message may be used.

At step 86, if the query/message is determined to be not authentic, themessage is discarded at step 82. If the query/message is determined tobe authentic (at step 86), it is determined, at step 88, if there is amatch between information contained (stored) in the device and the typeof information being sought. For example a match could pertain to datatype, value attributes, contextual attributes (e.g., time of collection,location of collection, etc.), or the like, of information pertaining toenvironmental parameters, temperature, humidity, rainfall, heatsignatures, video, audio, seismic activity, wind conditions, or thelike.

If it is determined, at step 88, that there is no match betweeninformation contained (stored) in the device and the type of informationbeing sought, the process ends at step 90.

If it is determined, at step 88, that there is a match betweeninformation contained (stored) in the device and the type of informationbeing sought, a response, or responses, is generated at step 92. Forexample, the device can package matching data and/or properties into oneor more response messages. A response message could include, forexample, a list of data, a summarization of data, an abstraction ofdata, or the like, or any appropriate combination thereof. Prior topackaging, various processes could be applied, such as, for example,noise reduction, smoothing, filtering, or the like. In an exampleembodiment, packaging comprises converting information into atransmittable format, such as, for example, byte-wise encoding (e.g.,base 64, MIME, etc.). At step 94 a digital signature, or the like, isgenerated from the response(s) and applied to the response(s). Thus, ifmultiple responses are generated, multiple digital signatures can begenerated and applied, respectively. The response message(s) can,optionally, be encrypted at step 94. The response is, or responses are,geocast at step 96. In an example embodiment, the device can geocast theresponse message, or messages, to the region, or regions, locationextracted from the query message, such as, for example, the locationfrom which the querier sent the query. In an example embodiment, thegeocast response(s) could contain information extracted from the querymessage, such as, for example, the identity of querier, a time of query,a sequence number, etc.

FIG. 7 is a flow diagram of another example process foracquiring/accessing information via a geocast protocol utilizing reversepath forwarding. A query is generated at step 100. The query cancomprise a message that includes, as described above, an indication of ageographic region, an indication of a temporal condition (e.g., timeframe, start time, end time), an indication as to the type ofinformation sought, or any combination thereof. The message can containa description of the desired information (information beingsought—wanted information), a digital signature, or the like, forauthentication purposes, or a combination thereof. The indication as tothe type of information sought can be indicative of any appropriateinformation as described herein. Optionally, the message can beencrypted.

The path of the message is initialized at step 102. The path isinitialized with an indication of the device sending the message. Thus,an indication of the device sending the message is included in themessage.

The message is geocast at step 104. The message can be geocast to anyappropriate region, location, or the like. The geocast message isreceived by a device at step 106. It is to be understood that thegeocast query can be received by multiple devices and the processdepicted by steps 106 et seq. in FIG. 7 could occur for each device thatreceives the geocast message. If the message of the query was encrypted(step 100), the device attempts to decrypt the message at step 110. Ifthe attempt to decrypt the message is not successful (step 112), themessage is discarded at step 118. If the attempt to decrypt the messageis successful (step 112), the query/message is verified at step 114. Themessage can be verified to determine if the message is authentic. In anexample configuration, the message is verified utilizing the digitalsignature that was included when generating the message (e.g., step100). Verification utilizing a digital signature can be accomplished viaany appropriate mechanism as known. For example, the message, the query,or any appropriate portion or portions thereof can be operated on by ahash function to obtain a first hash value. The first hash value can beincluded with the query. The first hash value may or may not beencrypted. At step 114, the same portion or portions of the messageand/or query can be operated on by the same hash function to obtain asecond hash value. If the first hash value is the same as the secondhash value, the query/message can be determined to be authentic. If thefirst hash value is not the same as the second hash value, thequery/message can be determined not to be authentic. It is to beunderstood that the foregoing description of verifying the query/messageis an example, and not limiting. Any appropriate mechanism or techniquefor verifying the query/message may be used.

At step 116, if the query/message is determined to be not authentic, themessage is discarded at step 118. If the query/message is determined tobe authentic (at step 116), the process proceeds along two paths. If thequery/message is determined to be authentic (at step 116), the currentdevice is added to the message path at step 120. That is, an indicationof the current device is added to the message. From step 120, theprocess proceeds to step 126 described below. Additionally, if thequery/message is determined to be authentic (at step 116), it isdetermined, at step 122, if there is a match between informationcontained (stored) in the device and the type of information beingsought. For example a match could pertain to data type, valueattributes, contextual attributes (e.g., time of collection, location ofcollection, etc.), or the like, of information pertaining toenvironmental parameters, temperature, humidity, rainfall, heatsignatures, video, audio, seismic activity, wind conditions, or thelike.

If it is determined, at step 122, that there is no match betweeninformation contained (stored) in the device and the type of informationbeing sought, no response is sent (step 129). The determination as towhether the message is to be retransmitted can be in accordance with theexample descriptions of retransmission determination as described hereinand/or as described in the aforementioned U.S. Pat. No. 7,525,933.

If the message is to be retransmitted (step 126), at step 128 a digitalsignature, or the like, may be generated from the message, portion,and/or portions thereof, and applied to the message. The responsemessage can, optionally, be encrypted at step 128. The message isretransmitted at step 130. Therefrom, the process proceeds to step 106and proceeds as previously described. If, at step 126, it is determinedthat the message is not to be retransmitted, the message is discardedate step 127.

If it is determined, at step 122, that there is a match betweeninformation contained (stored) in the device and the type of informationbeing sought, a response, or responses, is generated at step 124. Forexample, the device can package matching data and/or properties into oneor more response messages. A response message could include, forexample, a list of data, a summarization of data, an abstraction ofdata, or the like, or any appropriate combination thereof. Prior topackaging, various processes could be applied, such as, for example,noise reduction, smoothing, filtering, or the like. In an exampleembodiment, packaging comprises converting information into atransmittable format, such as, for example, byte-wise encoding (e.g.,base 64, MIME, etc.). From step 124, the process proceeds to step 132wherein the message path is extracted from the message. Thus, in anexample embodiment, a list of all previous devices in the path isobtained from the message. The message path is reversed at step 134, andthe message/response(s) is unicast using the reversed message path.Thus, in an example embodiment, the current device can transmit asource-routed unicast message/response(s) using the reverse message pathas the source route.

FIG. 8 is a flow diagram of an example process of geocast-basedcommand/control messaging. A command message is generated at step 150.The command message can comprise, for example, a command script message.The command can be indicative of any appropriate command or commands,for example, set off an alarm sound (e.g., looking for people underrubble), downloading data, load software, restart, or the like. In anexample embodiment, the command message can contain a digital signature,or the like, for authentication purposes. Optionally, the commandmessage can be encrypted.

The command message is geocast at step 152. The command message can begeocast to any appropriate region, location, or the like. The geocastmessage is received by a device at step 154. It is to be understood thatthe command message query can be received by multiple devices and theprocess depicted by steps 154 et seq. in FIG. 8 could occur for eachdevice that receives the geocast command message. If the command messagewas encrypted (step 150), the device attempts to decrypt the commandmessage at step 160. If the attempt to decrypt the command message isnot successful (step 162), the command message is discarded at step 164.If the attempt to decrypt the command message is successful (step 162),the command message is verified at step 158. The command message can beverified to determine if the command message is authentic. In an exampleconfiguration, the command message is verified utilizing the digitalsignature that was included when generating the command message (e.g.,step 150). Verification utilizing a digital signature can beaccomplished via any appropriate mechanism as known. For example, thecommand message, or any appropriate portion or portions thereof can beoperated on by a hash function to obtain a first hash value. The firsthash value can be included with the command message. The first hashvalue may or may not be encrypted. At step 158, the same portion orportions of the command message can be operated on by the same hashfunction to obtain a second hash value. If the first hash value is thesame as the second hash value, the command message can be determined tobe authentic. If the first hash value is not the same as the second hashvalue, the command message can be determined not to be authentic. It isto be understood that the foregoing description of verifying the commandmessage is an example, and not limiting. Any appropriate mechanism ortechnique for verifying the command message may be used.

At step 166, if the command message is determined to be not authentic,the message is discarded at step 164. If the command message isdetermined to be authentic (at step 166), the command (e.g., the commandscript) is executed at step 168.

FIG. 9 is a flow diagram of another example process foracquiring/accessing information via a geocast protocol. In an exampleembodiment, a device that is not capable of determining its own locationmay adopt a location of another device, and use the adopted location asits own. A beacon message is geocast at step 180. In an exampleembodiment, the beacon message comprises an indication of the anidentifier of the device's location, an indication of an identifier ofthe geocasting device, a geographic location of the geocasting device,or any appropriate combination thereof. A beacon message can be geocastby any number of devices. A beacon message can be geocast periodically,aperiodically, randomly, as trigger by an event (e.g., command), or anyappropriate combination thereof.

Another device (other than the device that geocasted the beacon message)monitors for transmissions at step 182. A beacon message is received bythe device at step 184. At step 184, it is determined if the device islocation aware. That is, it is determined if the device is a locationblind device. A location blind device (or location unaware device) is adevice that does not possess the capability to determine its location.And, a location aware device is a device that possesses the capabilityto determine its location. The determination as to whether a device islocation aware can be made in any appropriate manner. For example, thedevice could attempt to determine it location. If the attempt fails, thedevice can determine that it is location unaware (location blinddevice). If the attempt is successful, the device can determine that itis location aware (not a location blind device). In another exampleembodiment, the device could be preconfigured with a status indicator(bit or the like) indicating whether the device is location aware orlocation unaware. This status indicator could be analyzed at step 186.

If it is determined, at step 186, that the device is location unaware,the beacon message is discarded at step 188. If it is determined, atstep 186, that the device is location aware, information in the deviceis updated at step 190. As previously described, multiple devices cangeocast messages, and a receiving device could receive multiple beaconmessages. Accordingly, at step 190, information in the receiving deviceis update with information contained in each beacon message is received.And, in an example embodiment, the information could be updated with thelocations of multiple devices.

The receiving device selects one of the devices from which it received abeacon message as the device, whose location it will adopt. Theselection can be based on any appropriate criteria. For example, if abeacon message is received from only one device, the one device isselected. As examples of other selection criteria, the closest device tothe receiving device could be selected (e.g., determined by signalstrength or the like), the device that geocast the most recentlyreceived beacon message could be selected, the receiving device could beprogrammed to select a particular device (or group of devices), thereceiving device could randomly select a device, or the like, or anyappropriate combination thereof.

The receiving device adopts the location of the selected device as itsown location at step 194. The receiving device can participate in anyand/or all geocast activities as described herein, utilizing the adoptedlocation.

At step 196, it is determined if the receiving device wants to updateits adopted location. This may be the case, for example, in which deviceare known and/or expected to move (e.g., drift). If it is determined, astep 196, that the adopted location is to be updated, the processproceeds to step 182 and proceeds therefrom as previously described.).If it is determined, a step 196, that the adopted location is to beupdated, the process ends at step 198.

FIG. 10 is a block diagram of an example wireless communications device,also referred to as a sensor 200, that is configurable to facilitateinformation acquisition via a scalable wireless geocast protocol, asdescribed herein. The device/sensor 200 can include any appropriatedevice, mechanism, software, and/or hardware for facilitatinginformation acquisition via a scalable wireless geocast protocol asdescribed herein. As described herein, the device/sensor 200 compriseshardware, or a combination of hardware and software. And, each portionof the device/sensor 200 comprises hardware, or a combination ofhardware and software. In an example configuration, the device/sensor200 can comprise a processing portion 202, a memory portion 204, aninput/output portion 206, a user interface (UI) portion 208, and asensor portion 210 comprising at least one of a video camera portion212, a force/wave sensor 214, a microphone 216, a moisture sensor 218,or a combination thereof. The force/wave sensor 214 comprises at leastone of a motion detector, an accelerometer, an acoustic sensor, a tiltsensor, a pressure sensor, a temperature sensor, or the like. The motiondetector is configured to detect motion occurring outside of thecommunications device, for example via disturbance of a standing wave,via electromagnetic and/or acoustic energy, or the like. The acceleratoris capable of sensing acceleration, motion, and/or movement of thecommunications device. The acoustic sensor is capable of sensingacoustic energy, such as a noise, voice, etc., for example. The tiltsensor is capable of detecting a tilt of the communications device. Thepressure sensor is capable of sensing pressure against thecommunications device, such as from a shock wave caused by broken glassor the like. The temperature sensor is capable of sensing a measuringtemperature, such as inside of the vehicle, room, building, or the like.The moisture sensor 218 is capable of detecting moisture, such asdetecting if the device/sensor 200 is submerged in a liquid. Theprocessing portion 202, memory portion 204, input/output portion 206,user interface (UI) portion 208, video camera portion 212, force/wavesensor 214, and microphone 216 are coupled together to allowcommunications therebetween (coupling not shown in FIG. 10). Thedevice/sensor 200 also can comprise a timer (not depicted in FIG. 10).

In various embodiments, the input/output portion 206 comprises areceiver of the device/sensor 200, a transmitter of the device/sensor200, or a combination thereof. The input/output portion 206 is capableof, in conjunction with any other portion of the device/sensor 200 asneeded, receiving and/or providing information pertaining to informationacquisition via a scalable wireless geocast protocol, such as, forexample, a query, a response to a query, a retransmitted query, aretransmitted response to a query, or the like, as described herein. Theinput/output portion 206 also is capable of communications with otherdevices/sensors, as described herein. For example, the input/outputportion 206 can include a wireless communications (e.g., 2.5G/3G/4G) SIMcard. The input/output portion 206 is capable of receiving and/orsending text information, video information, audio information, controlinformation, image information, data, or any combination thereof. In anexample embodiment, the input/output portion 206 is capable of receivingand/or sending information to determine a location of the device/sensor200. In an example configuration, the input\output portion 206 comprisesa GPS receiver. In an example configuration, the device/sensor 200 candetermine its own geographical location through any type of locationdetermination system including, for example, the Global PositioningSystem (GPS), assisted GPS (A-GPS), time difference of arrivalcalculations, configured constant location (in the case of non-movingdevices), any combination thereof, or any other appropriate means. Invarious configurations, the input/output portion 206 can receive and/orprovide information via any appropriate means, such as, for example,optical means (e.g., infrared), electromagnetic means (e.g., RF, WI-FI,BLUETOOTH, ZIGBEE, etc.), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), or a combination thereof.In an example configuration, the input/output portion comprises a WIFIfinder, a two way GPS chipset or equivalent, or the like.

The processing portion 202 is capable of facilitating informationacquisition via a scalable wireless geocast protocol, as describedherein. For example, the processing portion 202 is capable of, inconjunction with any other portion of the device/sensor 200 as needed,generating a geocast message, generating a query, processing a query,processing a query response, determining if an indication of a region iscontained in a geocast message, determining if an indication of atemporal condition is contained in a geocast message, determining if anindication of a type of information sought is contained in a geocastmessage, determining if the device/sensor 200 is within a region,determining if the device/sensor 200 is capable of obtaining the type ofinformation sought, determining if the device/sensor 200 has obtainedinformation in accordance with temporal conditions, or the like, or anycombination thereof. The processing portion 202, in conjunction with anyother portion of the device/sensor 200, can provide the ability forusers/subscribers to enable, disable, and configure various features ofan application for information acquisition via a scalable wirelessgeocast protocol, as described herein. The processing portion 202, inconjunction with any other portion of the device/sensor 200 as needed,can enable the device/sensor 200 to covert speech to text when it isconfigured to send text messages. In an example embodiment, theprocessing portion 202, in conjunction with any other portion of thedevice/sensor 200 as needed, can convert text to speech for renderingvia the user interface portion 208.

In a basic configuration, the device/sensor 200 can include at least onememory portion 204. The memory portion 204 can store any informationutilized in conjunction with information acquisition via a scalablewireless geocast protocol, as described herein. For example, the memoryportion 204 is capable of storing information pertaining to a geocastmessage, a query, a query response, an indication of a region, anindication of a temporal condition, an indication of a type ofinformation sought, geocast parameters, text/voice message, anaudio/text message, subscriber profile information, subscriberidentification information, phone numbers, an identification code of thedevice/sensor, video information, audio information, controlinformation, information indicative of sensor data (e.g., raw individualsensor information, combination of sensor information, processed sensorinformation, etc.), or a combination thereof. Depending upon the exactconfiguration and type of processor, the memory portion 204 can bevolatile (such as some types of RAM), non-volatile (such as ROM, flashmemory, etc.). The device/sensor 200 can include additional storage(e.g., removable storage and/or non-removable storage) including, tape,flash memory, smart cards, CD-ROM, digital versatile disks (DVD) orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, universal serial bus (USB)compatible memory, or the like. In an example configuration, the memoryportion 204, or a portion of the memory portion 202 is hardened suchthat information stored therein can be recovered if the device/sensor200 is exposed to extreme heat, extreme vibration, extreme moisture,corrosive chemicals or gas, or the like. In an example configuration,the information stored in the hardened portion of the memory portion 204is encrypted, or otherwise rendered unintelligible without use of anappropriate cryptographic key, password, biometric (voiceprint,fingerprint, retinal image, facial image, or the like). Wherein, use ofthe appropriate cryptographic key, password, biometric will render theinformation stored in the hardened portion of the memory portion 204intelligible.

The device/sensor 200 also can contain a UI portion 208 allowing a userto communicate with the device/sensor 200. The UI portion 208 is capableof rendering any information utilized in conjunction with informationacquisition via a scalable wireless geocast protocol as describedherein. For example, the UI portion 208 can provide means for enteringtext, entering a phone number, rendering text, rendering images,rendering multimedia, rendering sound, rendering video, receiving sound,or the like, as described herein. The UI portion 208 can provide theability to control the device/sensor 200, via, for example, buttons,soft keys, voice actuated controls, a touch screen, movement of themobile device/sensor 200, visual cues (e.g., moving a hand in front of acamera on the mobile device/sensor 200), or the like. The UI portion 208can provide visual information (e.g., via a display), audio information(e.g., via speaker), mechanically (e.g., via a vibrating mechanism), ora combination thereof. In various configurations, the UI portion 208 cancomprise a display, a touch screen, a keyboard, a speaker, or anycombination thereof. The UI portion 208 can comprise means for inputtingbiometric information, such as, for example, fingerprint information,retinal information, voice information, and/or facial characteristicinformation. The UI portion 208 can be utilized to enter an indicationof the designated destination (e.g., the phone number, IP address,geographic information, or the like).

In an example embodiment, the sensor portion 210 of the device/sensor200 comprises the video camera portion 212, the force/wave sensor 214,and the microphone 216. The video camera portion 212 comprises a camera(or cameras) and associated equipment capable of capturing still imagesand/or video and to provide the captured still images and/or video toother portions of the device/sensor 200. In an example embodiment, theforce/wave sensor 214 comprises an accelerometer, a tilt sensor, anacoustic sensor capable of sensing acoustic energy, an optical sensor(e.g., infrared), or any combination thereof.

Although not necessary to implement information acquisition via ascalable wireless geocast protocol, a device/sensor can be part ofand/or in communications with various wireless communications networks.Some of which are described below.

FIG. 11 depicts an overall block diagram of an exemplary packet-basedmobile cellular network environment, such as a GPRS network, withinwhich information acquisition via a scalable wireless geocast protocolcan be implemented. In the exemplary packet-based mobile cellularnetwork environment shown in FIG. 11, there are a plurality of BaseStation Subsystems (“BSS”) 1100 (only one is shown), each of whichcomprises a Base Station Controller (“BSC”) 1102 serving a plurality ofBase Transceiver Stations (“BTS”) such as BTSs 1104, 1106, and 1108.BTSs 1104, 1106, 1108, etc. are the access points where users ofpacket-based mobile devices become connected to the wireless network. Inexemplary fashion, the packet traffic originating from user devices istransported via an over-the-air interface to a BTS 1108, and from theBTS 1108 to the BSC 1102. Base station subsystems, such as BSS 1100, area part of internal frame relay network 1110 that can include ServiceGPRS Support Nodes (“SGSN”) such as SGSN 1112 and 1114. Each SGSN isconnected to an internal packet network 1120 through which a SGSN 1112,1114, etc. can route data packets to and from a plurality of gatewayGPRS support nodes (GGSN) 1122, 1124, 1126, etc. As illustrated, SGSN1114 and GGSNs 1122, 1124, and 1126 are part of internal packet network1120. Gateway GPRS serving nodes 1122, 1124 and 1126 mainly provide aninterface to external Internet Protocol (“IP”) networks such as PublicLand Mobile Network (“PLMN”) 1150, corporate intranets 1140, orFixed-End System (“FES”) or the public Internet 1130. As illustrated,subscriber corporate network 1140 may be connected to GGSN 1124 viafirewall 1132; and PLMN 1150 is connected to GGSN 1124 via boardergateway router 1134. The Remote Authentication Dial-In User Service(“RADIUS”) server 1142 may be used for caller authentication when a userof a mobile cellular device calls corporate network 1140.

Generally, there can be a several cell sizes in a GSM network, referredto as macro, micro, pico, femto and umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro-cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential, or smallbusiness environments. On the other hand, umbrella cells are used tocover shadowed regions of smaller cells and fill in gaps in coveragebetween those cells.

FIG. 12 illustrates an architecture of a typical GPRS network withinwhich information acquisition via a scalable wireless geocast protocolcan be implemented. The architecture depicted in FIG. 12 is segmentedinto four groups: users 1250, radio access network 1260, core network1270, and interconnect network 1280. Users 1250 comprise a plurality ofend users. Note, device 1212 is referred to as a mobile subscriber inthe description of network shown in FIG. 12. In an example embodiment,the device depicted as mobile subscriber 1212 comprises a communicationsdevice (e.g., device/sensor 70). Radio access network 1260 comprises aplurality of base station subsystems such as BSSs 1262, which includeBTSs 1264 and BSCs 1266. Core network 1270 comprises a host of variousnetwork elements. As illustrated in FIG. 12, core network 1270 maycomprise Mobile Switching Center (“MSC”) 1271, Service Control Point(“SCP”) 1272, gateway MSC 1273, SGSN 1276, Home Location Register(“HLR”) 1274, Authentication Center (“AuC”) 1275, Domain Name Server(“DNS”) 1277, and GGSN 1278. Interconnect network 1280 also comprises ahost of various networks and other network elements. As illustrated inFIG. 12, interconnect network 1280 comprises Public Switched TelephoneNetwork (“PSTN”) 1282, Fixed-End System (“FES”) or Internet 1284,firewall 1288, and Corporate Network 1289.

A mobile switching center can be connected to a large number of basestation controllers. At MSC 1271, for instance, depending on the type oftraffic, the traffic may be separated in that voice may be sent toPublic Switched Telephone Network (“PSTN”) 1282 through Gateway MSC(“GMSC”) 1273, and/or data may be sent to SGSN 1276, which then sendsthe data traffic to GGSN 1278 for further forwarding.

When MSC 1271 receives call traffic, for example, from BSC 1266, itsends a query to a database hosted by SCP 1272. The SCP 1272 processesthe request and issues a response to MSC 1271 so that it may continuecall processing as appropriate.

The HLR 1274 is a centralized database for users to register to the GPRSnetwork. HLR 1274 stores static information about the subscribers suchas the International Mobile Subscriber Identity (“IMSI”), subscribedservices, and a key for authenticating the subscriber. HLR 1274 alsostores dynamic subscriber information such as the current location ofthe mobile subscriber. Associated with HLR 1274 is AuC 1275. AuC 1275 isa database that contains the algorithms for authenticating subscribersand includes the associated keys for encryption to safeguard the userinput for authentication.

In the following, depending on context, the term “mobile subscriber”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 12, whenmobile subscriber 1212 initiates the attach process by turning on thenetwork capabilities of the mobile device, an attach request is sent bymobile subscriber 1212 to SGSN 1276. The SGSN 1276 queries another SGSN,to which mobile subscriber 1212 was attached before, for the identity ofmobile subscriber 1212. Upon receiving the identity of mobile subscriber1212 from the other SGSN, SGSN 1276 requests more information frommobile subscriber 1212. This information is used to authenticate mobilesubscriber 1212 to SGSN 1276 by HLR 1274. Once verified, SGSN 1276 sendsa location update to HLR 1274 indicating the change of location to a newSGSN, in this case SGSN 1276. HLR 1274 notifies the old SGSN, to whichmobile subscriber 1212 was attached before, to cancel the locationprocess for mobile subscriber 1212. HLR 1274 then notifies SGSN 1276that the location update has been performed. At this time, SGSN 1276sends an Attach Accept message to mobile subscriber 1212, which in turnsends an Attach Complete message to SGSN 1276.

After attaching itself with the network, mobile subscriber 1212 thengoes through the authentication process. In the authentication process,SGSN 1276 sends the authentication information to HLR 1274, which sendsinformation back to SGSN 1276 based on the user profile that was part ofthe user's initial setup. The SGSN 1276 then sends a request forauthentication and ciphering to mobile subscriber 1212. The mobilesubscriber 1212 uses an algorithm to send the user identification (ID)and password to SGSN 1276. The SGSN 1276 uses the same algorithm andcompares the result. If a match occurs, SGSN 1276 authenticates mobilesubscriber 1212.

Next, the mobile subscriber 1212 establishes a user session with thedestination network, corporate network 1289, by going through a PacketData Protocol (“PDP”) activation process. Briefly, in the process,mobile subscriber 1212 requests access to the Access Point Name (“APN”),for example, UPS.com, and SGSN 1276 receives the activation request frommobile subscriber 1212. SGSN 1276 then initiates a Domain Name Service(“DNS”) query to learn which GGSN node has access to the UPS.com APN.The DNS query is sent to the DNS server within the core network 1270,such as DNS 1277, which is provisioned to map to one or more GGSN nodesin the core network 1270. Based on the APN, the mapped GGSN 1278 canaccess the requested corporate network 1289. The SGSN 1276 then sends toGGSN 1278 a Create Packet Data Protocol (“PDP”) Context Request messagethat contains necessary information. The GGSN 1278 sends a Create PDPContext Response message to SGSN 1276, which then sends an Activate PDPContext Accept message to mobile subscriber 1212.

Once activated, data packets of the call made by mobile subscriber 1212can then go through radio access network 1260, core network 1270, andinterconnect network 1280, in a particular fixed-end system or Internet1284 and firewall 1288, to reach corporate network 1289.

FIG. 13 illustrates an exemplary block diagram view of a GSM/GPRS/IPmultimedia network architecture within information acquisition via ascalable wireless geocast protocol can be implemented. As illustrated,the architecture of FIG. 13 includes a GSM core network 1301, a GPRSnetwork 1330 and an IP multimedia network 1338. The GSM core network1301 includes a Mobile Station (MS) 1302, at least one Base TransceiverStation (BTS) 1304 and a Base Station Controller (BSC) 1306. The MS 1302is physical equipment or Mobile Equipment (ME), such as a mobile phoneor a laptop computer that is used by mobile subscribers, with aSubscriber identity Module (SIM) or a Universal Integrated Circuit Card(UICC). The SIM or UICC includes an International Mobile SubscriberIdentity (IMSI), which is a unique identifier of a subscriber. The BTS1304 is physical equipment, such as a radio tower, that enables a radiointerface to communicate with the MS. Each BTS may serve more than oneMS. The BSC 1306 manages radio resources, including the BTS. The BSC maybe connected to several BTSs. The BSC and BTS components, incombination, are generally referred to as a base station (BSS) or radioaccess network (RAN) 1303.

The GSM core network 1301 also includes a Mobile Switching Center (MSC)1308, a Gateway Mobile Switching Center (GMSC) 1310, a Home LocationRegister (HLR) 1312, Visitor Location Register (VLR) 1314, anAuthentication Center (AuC) 1318, and an Equipment Identity Register(EIR) 1316. The MSC 1308 performs a switching function for the network.The MSC also performs other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC1310 provides a gateway between the GSM network and other networks, suchas an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 1320. Thus, the GMSC 1310 providesinterworking functionality with external networks.

The HLR 1312 is a database that contains administrative informationregarding each subscriber registered in a corresponding GSM network. TheHLR 1312 also contains the current location of each MS. The VLR 1314 isa database that contains selected administrative information from theHLR 1312. The VLR contains information necessary for call control andprovision of subscribed services for each MS currently located in ageographical area controlled by the VLR. The HLR 1312 and the VLR 1314,together with the MSC 1308, provide the call routing and roamingcapabilities of GSM. The AuC 1316 provides the parameters needed forauthentication and encryption functions. Such parameters allowverification of a subscriber's identity. The EIR 1318 storessecurity-sensitive information about the mobile equipment.

A Short Message Service Center (SMSC) 1309 allows one-to-one ShortMessage Service (SMS) messages to be sent to/from the MS 1302. A PushProxy Gateway (PPG) 1311 is used to “push” (i.e., send without asynchronous request) content to the MS 1302. The PPG 1311 acts as aproxy between wired and wireless networks to facilitate pushing of datato the MS 1302. A Short Message Peer to Peer (SMPP) protocol router 1313is provided to convert SMS-based SMPP messages to cell broadcastmessages. SMPP is a protocol for exchanging SMS messages between SMSpeer entities such as short message service centers. The SMPP protocolis often used to allow third parties, e.g., content suppliers such asnews organizations, to submit bulk messages.

To gain access to GSM services, such as speech, data, and short messageservice (SMS), the MS first registers with the network to indicate itscurrent location by performing a location update and IMSI attachprocedure. The MS 1302 sends a location update including its currentlocation information to the MSC/VLR, via the BTS 1304 and the BSC 1306.The location information is then sent to the MS's HLR. The HLR isupdated with the location information received from the MSC/VLR. Thelocation update also is performed when the MS moves to a new locationarea. Typically, the location update is periodically performed to updatethe database as location updating events occur.

The GPRS network 1330 is logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 1332, a cell broadcast and a GatewayGPRS support node (GGSN) 1334. The SGSN 1332 is at the same hierarchicallevel as the MSC 1308 in the GSM network. The SGSN controls theconnection between the GPRS network and the MS 1302. The SGSN also keepstrack of individual MS's locations and security functions and accesscontrols.

A Cell Broadcast Center (CBC) 1317 communicates cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile phone customers who arelocated within a given part of its network coverage area at the time themessage is broadcast.

The GGSN 1334 provides a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 1336. That is, the GGSNprovides interworking functionality with external networks, and sets upa logical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it is transferred to an external TCP-IP network1336, such as an X.25 network or the Internet. In order to access GPRSservices, the MS first attaches itself to the GPRS network by performingan attach procedure. The MS then activates a packet data protocol (PDP)context, thus activating a packet communication session between the MS,the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services can be used inparallel. The MS can operate in one of three classes: class A, class B,and class C. A class A MS can attach to the network for both GPRSservices and GSM services simultaneously. A class A MS also supportssimultaneous operation of GPRS services and GSM services. For example,class A mobiles can receive GSM voice/data/SMS calls and GPRS data callsat the same time.

A class B MS can attach to the network for both GPRS services and GSMservices simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time.

A class C MS can attach for only one of the GPRS services and GSMservices at a time. Simultaneous attachment and operation of GPRSservices and GSM services is not possible with a class C MS.

A GPRS network 1330 can be designed to operate in three networkoperation modes (NOM1, NOM2 and NOM3). A network operation mode of aGPRS network is indicated by a parameter in system information messagestransmitted within a cell. The system information messages dictates a MSwhere to listen for paging messages and how to signal towards thenetwork. The network operation mode represents the capabilities of theGPRS network. In a NOM1 network, a MS can receive pages from a circuitswitched domain (voice call) when engaged in a data call. The MS cansuspend the data call or take both simultaneously, depending on theability of the MS. In a NOM2 network, a MS may not receive pages from acircuit switched domain when engaged in a data call, since the MS isreceiving data and is not listening to a paging channel. In a NOM3network, a MS can monitor pages for a circuit switched network whilereceived data and vice versa.

The IP multimedia network 1338 was introduced with 3GPP Release 5, andincludes an IP multimedia subsystem (IMS) 1340 to provide richmultimedia services to end users. A representative set of the networkentities within the IMS 1340 are a call/session control function (CSCF),a media gateway control function (MGCF) 1346, a media gateway (MGW)1348, and a master subscriber database, called a home subscriber server(HSS) 1350. The HSS 1350 may be common to the GSM network 1301, the GPRSnetwork 1330 as well as the IP multimedia network 1338.

The IP multimedia system 1340 is built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)1343, a proxy CSCF (P-CSCF) 1342, and a serving CSCF (S-CSCF) 1344. TheP-CSCF 1342 is the MS's first point of contact with the IMS 1340. TheP-CSCF 1342 forwards session initiation protocol (SIP) messages receivedfrom the MS to an SIP server in a home network (and vice versa) of theMS. The P-CSCF 1342 may also modify an outgoing request according to aset of rules defined by the network operator (for example, addressanalysis and potential modification).

The I-CSCF 1343, forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. The I-CSCF 1343 may contact asubscriber location function (SLF) 1345 to determine which HSS 1350 touse for the particular subscriber, if multiple HSS's 1350 are present.The S-CSCF 1344 performs the session control services for the MS 1302.This includes routing originating sessions to external networks androuting terminating sessions to visited networks. The S-CSCF 1344 alsodecides whether an application server (AS) 1352 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision is based on information received fromthe HSS 1350 (or other sources, such as an application server 1352). TheAS 1352 also communicates to a location server 1356 (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of the MS 1302.

The HSS 1350 contains a subscriber profile and keeps track of which corenetwork node is currently handling the subscriber. It also supportssubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 1350, a subscriber location function providesinformation on the HSS 1350 that contains the profile of a givensubscriber.

The MGCF 1346 provides interworking functionality between SIP sessioncontrol signaling from the IMS 1340 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown). It also controls the mediagateway (MGW) 1348 that provides user-plane interworking functionality(e.g., converting between AMR- and PCM-coded voice). The MGW 1348 alsocommunicates with other IP multimedia networks 1354.

Push to Talk over Cellular (PoC) capable mobile phones register with thewireless network when the phones are in a predefined area (e.g., jobsite, etc.). When the mobile phones leave the area, they register withthe network in their new location as being outside the predefined area.This registration, however, does not indicate the actual physicallocation of the mobile phones outside the pre-defined area.

FIG. 14 illustrates a PLMN block diagram view of an exemplaryarchitecture in which the information acquisition via a scalablewireless geocast protocol may be incorporated. Mobile Station (MS) 1401is the physical equipment used by the PLMN subscriber. In oneillustrative embodiment, WT 200 and/or communications device 120 mayserve as Mobile Station 1401. Mobile Station 1401 may be one of, but notlimited to, a cellular telephone, a cellular telephone in combinationwith another electronic device or any other wireless mobilecommunication device.

Mobile Station 1401 may communicate wirelessly with Base Station System(BSS) 1410. BSS 1410 contains a Base Station Controller (BSC) 1411 and aBase Transceiver Station (BTS) 1412. BSS 1410 may include a single BSC1411/BTS 1412 pair (Base Station) or a system of BSC/BTS pairs which arepart of a larger network. BSS 1410 is responsible for communicating withMobile Station 1401 and may support one or more cells. BSS 1410 isresponsible for handling cellular traffic and signaling between MobileStation 1401 and Core Network 1440. Typically, BSS 1410 performsfunctions that include, but are not limited to, digital conversion ofspeech channels, allocation of channels to mobile devices, paging, andtransmission/reception of cellular signals.

Additionally, Mobile Station 1401 may communicate wirelessly with RadioNetwork System (RNS) 1420. RNS 1420 contains a Radio Network Controller(RNC) 1421 and one or more Node(s) B 1422. RNS 1420 may support one ormore cells. RNS 1420 may also include one or more RNC 1421/Node B 1422pairs or alternatively a single RNC 1421 may manage multiple Nodes B1422. RNS 1420 is responsible for communicating with Mobile Station 1401in its geographically defined area. RNC 1421 is responsible forcontrolling the Node(s) B 1422 that are connected to it and is a controlelement in a UMTS radio access network. RNC 1421 performs functions suchas, but not limited to, load control, packet scheduling, handovercontrol, security functions, as well as controlling Mobile Station1401's access to the Core Network (CN) 1440.

The evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 1430 is aradio access network that provides wireless data communications forMobile Station 1401 and User Equipment 1402. E-UTRAN 1430 provideshigher data rates than traditional UMTS. It is part of the Long TermEvolution (LTE) upgrade for mobile networks and later releases meet therequirements of the International Mobile Telecommunications (IMT)Advanced and are commonly known as a 4G networks. E-UTRAN 1430 mayinclude of series of logical network components such as E-UTRAN Node B(eNB) 1431 and E-UTRAN Node B (eNB) 1432. E-UTRAN 1430 may contain oneor more eNBs. User Equipment 1402 may be any user device capable ofconnecting to E-UTRAN 1430 including, but not limited to, a personalcomputer, laptop, mobile device, wireless router, or other devicecapable of wireless connectivity to E-UTRAN 1430. The improvedperformance of the E-UTRAN 1430 relative to a typical UMTS networkallows for increased bandwidth, spectral efficiency, and functionalityincluding, but not limited to, voice, high-speed applications, largedata transfer and IPTV, while still allowing for full mobility.

An exemplary embodiment of a mobile data and communication service thatmay be implemented in the PLMN architecture described in FIG. 14 is theEnhanced Data rates for GSM Evolution (EDGE). EDGE is an enhancement forGPRS networks that implements an improved signal modulation scheme knownas 8-PSK (Phase Shift Keying). By increasing network utilization, EDGEmay achieve up to three times faster data rates as compared to a typicalGPRS network. EDGE may be implemented on any GSM network capable ofhosting a GPRS network, making it an ideal upgrade over GPRS since itmay provide increased functionality of existing network resources.Evolved EDGE networks are becoming standardized in later releases of theradio telecommunication standards, which provide for even greaterefficiency and peak data rates of up to 1 Mbit/s, while still allowingimplementation on existing GPRS-capable network infrastructure.

Typically Mobile Station 1401 may communicate with any or all of BSS1410, RNS 1420, or E-UTRAN 1430. In a illustrative system, each of BSS1410, RNS 1420, and E-UTRAN 1430 may provide Mobile Station 1401 withaccess to Core Network 1440. The Core Network 1440 may include of aseries of devices that route data and communications between end users.Core Network 1440 may provide network service functions to users in theCircuit Switched (CS) domain, the Packet Switched (PS) domain or both.The CS domain refers to connections in which dedicated network resourcesare allocated at the time of connection establishment and then releasedwhen the connection is terminated. The PS domain refers tocommunications and data transfers that make use of autonomous groupingsof bits called packets. Each packet may be routed, manipulated,processed or handled independently of all other packets in the PS domainand does not require dedicated network resources.

The Circuit Switched-Media Gateway Function (CS-MGW) 1441 is part ofCore Network 1440, and interacts with Visitor Location Register (VLR)and Mobile-Services Switching Center (MSC) Server 1460 and Gateway MSCServer 1461 in order to facilitate Core Network 1440 resource control inthe CS domain. Functions of CS-MGW 1441 include, but are not limited to,media conversion, bearer control, payload processing and other mobilenetwork processing such as handover or anchoring. CS-MGW 1440 mayreceive connections to Mobile Station 1401 through BSS 1410, RNS 1420 orboth.

Serving GPRS Support Node (SGSN) 1442 stores subscriber data regardingMobile Station 1401 in order to facilitate network functionality. SGSN1442 may store subscription information such as, but not limited to, theInternational Mobile Subscriber Identity (IMSI), temporary identities,or Packet Data Protocol (PDP) addresses. SGSN 1442 may also storelocation information such as, but not limited to, the Gateway GPRSSupport Node (GGSN) 1444 address for each GGSN where an active PDPexists. GGSN 1444 may implement a location register function to storesubscriber data it receives from SGSN 1442 such as subscription orlocation information.

Serving Gateway (S-GW) 1443 is an interface which provides connectivitybetween E-UTRAN 1430 and Core Network 1440. Functions of S-GW 1443include, but are not limited to, packet routing, packet forwarding,transport level packet processing, event reporting to Policy andCharging Rules Function (PCRF) 1450, and mobility anchoring forinter-network mobility. PCRF 1450 uses information gathered from S-GW1443, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources and other networkadministration functions. Packet Data Network Gateway (PDN-GW) 1445 mayprovide user-to-services connectivity functionality including, but notlimited to, network-wide mobility anchoring, bearer session anchoringand control, and IP address allocation for PS domain connections.

Home Subscriber Server (HSS) 1463 is a database for user information,and stores subscription data regarding Mobile Station 1401 or UserEquipment 1402 for handling calls or data sessions. Networks may containone HSS 1463 or more if additional resources are required. Exemplarydata stored by HSS 1463 include, but is not limited to, useridentification, numbering and addressing information, securityinformation, or location information. HSS 1463 may also provide call orsession establishment procedures in both the PS and CS domains.

The VLR/MSC Server 1460 provides user location functionality. WhenMobile Station 1401 enters a new network location, it begins aregistration procedure. A MSC Server for that location transfers thelocation information to the VLR for the area. A VLR and MSC Server maybe located in the same computing environment, as is shown by VLR/MSCServer 1460, or alternatively may be located in separate computingenvironments. A VLR may contain, but is not limited to, user informationsuch as the IMSI, the Temporary Mobile Station Identity (TMSI), theLocal Mobile Station Identity (LMSI), the last known location of themobile station, or the SGSN where the mobile station was previouslyregistered. The MSC server may contain information such as, but notlimited to, procedures for Mobile Station 1401 registration orprocedures for handover of Mobile Station 1401 to a different section ofthe Core Network 1440. GMSC Server 1461 may serve as a connection toalternate GMSC Servers for other mobile stations in larger networks.

Equipment Identity Register (EIR) 1462 is a logical element which maystore the International Mobile Equipment Identities (IMEI) for MobileStation 1401. In a typical embodiment, user equipment may be classifiedas either “white listed” or “black listed” depending on its status inthe network. In one embodiment, if Mobile Station 1401 is stolen and putto use by an unauthorized user, it may be registered as “black listed”in EIR 1462, preventing its use on the network. Mobility ManagementEntity (MME) 1464 is a control node which may track Mobile Station 1401or User Equipment 1402 if the devices are idle. Additional functionalitymay include the ability of MME 1464 to contact an idle Mobile Station1401 or User Equipment 1402 if retransmission of a previous session isrequired.

While example embodiments of information acquisition via a scalablewireless geocast protocol have been described in connection with variouscomputing devices/processors, the underlying concepts can be applied toany computing device, processor, or system capable of implementinginformation acquisition via a scalable wireless geocast protocol. Thevarious techniques described herein can be implemented in connectionwith hardware or software or, where appropriate, with a combination ofboth. Thus, the methods and apparatuses of information acquisition via ascalable wireless geocast protocol can be implemented, or certainaspects or portions thereof, can take the form of program code (i.e.,instructions) embodied in tangible storage media having a tangiblephysical structure. Examples of tangible storage media include floppydiskettes, CD-ROMs, DVDs, hard drives, or any other tangiblemachine-readable storage medium (tangible computer-readable storagemedium). Thus, a tangible storage medium as described herein is not atransient propagating signal. When the program code is loaded into andexecuted by a machine, such as a computer, the machine becomes anapparatus for implementing information acquisition via a scalablewireless geocast protocol. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile and non-volatile memory and/or storage elements), at least oneinput device, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and combined with hardwareimplementations.

The methods and apparatuses for information acquisition via a scalablewireless geocast protocol also can be practiced via communicationsembodied in the form of program code that is transmitted over sometransmission medium, such as over electrical wiring or cabling, throughfiber optics, or via any other form of transmission, wherein, when theprogram code is received and loaded into and executed by a machine, suchas an EPROM, a gate array, a programmable logic device (PLD), a clientcomputer, or the like, the machine becomes an apparatus for implementinginformation acquisition via a scalable wireless geocast protocol. Whenimplemented on a general-purpose processor, the program code combineswith the processor to provide a unique apparatus that operates to invokethe functionality of information acquisition via a scalable wirelessgeocast protocol.

While information acquisition via a scalable wireless geocast protocolhas been described in connection with the various embodiments of thevarious figures, it is to be understood that other similar embodimentscan be used or modifications and additions can be made to the describedembodiments for information acquisition via a scalable wireless geocastprotocol without deviating therefrom. For example, one skilled in theart will recognize that information acquisition via a scalable wirelessgeocast protocol as described in the present application may apply toany environment, whether wired or wireless, and may be applied to anynumber of such devices connected via a communications network andinteracting across the network. Therefore, information acquisition via ascalable wireless geocast protocol should not be limited to any singleembodiment, but rather should be construed in breadth and scope inaccordance with the appended claims.

What is claimed:
 1. A method comprising receiving, from a first sensor, in a mobile ad hoc network, a query message comprising a request for information, the query message comprising an indication of a region of intended reception of the query message, the region defined by a first defined size; altering the region of the first defined size to a region of a second defined size based on a number of sensors in the region of the first defined size; and responsive to determining that a second sensor is within the region of the second defined size, responding to the query message.
 2. The method of claim 1, wherein the information comprises video parameters.
 3. The method of claim 1, wherein the information comprises audio parameters.
 4. The method of claim 1, wherein the information comprises wind conditions parameters.
 5. The method of claim 1, wherein the information comprises temperature parameters.
 6. The method of claim 1, wherein the information comprises humidity parameters.
 7. The method of claim 1, wherein the information comprises heat signature parameters.
 8. The method of claim 1, wherein the information comprises seismic activity parameters.
 9. The method of claim 1, wherein the information comprises a temporal condition.
 10. The method of claim 1, wherein the information pertains to environmental parameters.
 11. The method of claim 1, further operations comprising providing to the first sensor, via a unicast over a reverse message path, a response to the query message based on a result of processing the query message.
 12. The method of claim 1, further operations comprising providing to the first sensor, via a unicast over a reverse message path, a response to the query message based on a result of processing the query message, wherein the reverse message path is described in the received query message.
 13. A non-transitory computer readable storage medium comprising computer executable instructions that when executed by a computing device cause said computing device to effectuate operations comprising: receiving, from a first sensor, in a mobile ad hoc network, a query message comprising a request for information, the query message comprising an indication of a region of intended reception of the query message, the region defined by a first defined size; altering the region of the first defined size to a region of a second defined size based on a number of sensors in the region of the first defined size; and responsive to determining that a second sensor is within the region of the second defined size, responding to the query message.
 14. The computer readable storage medium of claim 13, wherein the information comprises video, audio, wind conditions.
 15. The computer readable storage medium of claim 13, wherein the information comprises temperature, humidity, rainfall, or wind conditions.
 16. The computer readable storage medium of claim 13, wherein the information comprises seismic activity parameters.
 17. The computer readable storage medium of claim 13, wherein the information comprises heat signature parameters.
 18. The computer readable storage medium of claim 13, wherein the information comprises a temporal condition.
 19. The computer readable storage medium of claim 13, further operations comprising providing to the first sensor, via a unicast over a reverse message path, a response to the query message based on a result of processing the query message.
 20. The computer readable storage medium of claim 13, further operations comprising providing to the first sensor, via a unicast over a reverse message path, a response to the query message based on a result of processing the query message, wherein the reverse message path is described in the received query message. 